home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
CD ROM Paradise Collection 4
/
CD ROM Paradise Collection 4 1995 Nov.iso
/
program
/
tjgold.zip
/
INSTALL.004
/
GOLDREAD.ME
< prev
next >
Wrap
Text File
|
1995-07-16
|
14KB
|
350 lines
▐▀▀▀▌ ▌ ▐▄▄▄▄▄ ▐
▐ ▌ ▐ █ ▐▀▀
▐ ▐▀▀▀▌▐ ▌ ▐ █▐▀▀▀▌▐ ▐▀▀▀ █▀▀▀
▐ ▀▌▐ ▌▐ ▐▀▀▀▌ ▐ █▐ ▌▐ ▐▄▄ █▄▄▄
▐▄▄▄▌▐▄▄▄▌▐▄▄▄ ▐▄▄▄▌ ▐ █▐▄▄▄▌▐▄ ▐▄▄▄ ▄▄▄█
Welcome to Gold. This file contains important, late-breaking
information about the GOLD toolkit, including updates to the User
Manual and Reference.
TABLE OF CONTENTS
-----------------
1) ASP INFORMATION
2) RELEASE NOTES
3) ROYALTIES
4) ADVANTAGES OF REGISTERING GOLD
5) LIMITED DISTRIBUTION LICENSE
6) INSTALLING ONLINE HELP IN BP 7.0
7) NEW PROCEDURES AND FUNCTIONS
8) GOLD DUST
ARTICLE 0001 - DATABASE HANDLES
1) ASP INFORMATION
------------------
┌────────────────────────────────────────────────────────────────┐
│ │
│ ASP Ombudsman Information │
│ │
│ TechnoJock Software, Inc. is a member of the Association of │
│ Shareware Professionals (ASP). ASP wants to make sure that │
│ the shareware principle works for you. If you are unable │
│ to resolve a shareware-related problem with an ASP member │
│ by contacting the member directly, ASP may be able to help. │
│ The ASP ombudsman can help you resolve a dispute or problem │
│ with an ASP member, but does not provide technical support │
│ for members' products. Please write to the ASP Ombudsman at: │
│ ASP Ombudsman _______ │
│ 545 Grover Road ____|__ | (R) │
│ Muskegon, MI --| | |------------------- │
│ 49442-9427 (USA) | ____|__ | Association of │
│ or send a Compuserve | | |_| Shareware │
│ message via CompuServe |__| o | Professionals │
│ mail to 70475,1071, or -----| | |--------------------- │
│ a FAX to 616-788-2765. |___|___| MEMBER │
│ │
└────────────────────────────────────────────────────────────────┘
2) RELEASE NOTES
----------------
Gold 1.01 - Modified numerous units to make code compatible
with Turbo Pascal version 6.0
3) ROYALTIES
------------
The following text is extracted from the User's Guide, and only
applies to the registered version:
"Many Gold users develop commercial programs specifically
to sell for profit. TJ Software, Inc., neither expects
nor requires a royalty fee on such programs. The major
restriction is that you may not develop a program that is
itself a toolkit. In addition, neither the toolkit source
code nor the compiled units may be distributed or sold as
part of another product. If you have not registered your
copy of Gold, you may not develop programs for sale or
distribution. Refer to the license agreement at the front
of this manual for our definitive statement on royalties
and warranties."
Users of the Shareware version of the product may NOT distribute
any executable files created with GOLD. If you want to create EXE's
with GOLD for sale or for any form of distribution, you must register
your copy of GOLD.
4) What's the advantage of registering TTTGOLD?
-----------------------------------------------
Gold is distributed as a Shareware product. When you register
your copy of the program, you not only get the latest version
of the toolkit, you also receive the following bonus features:
Books You get two professionally bound and typeset manuals!
Desktop The desktop unit allows you to easily create desktop
applications with pulldown menus, status bar, etc.
Run DEMOVIEW.EXE to see a slick desktop in action.
Calculator Add a fully functional calculator to your apps with
a couple of lines of code. Run DEMOCALC.EXE to see
the calculator in action.
INI Unit This unit makes it a snap to add Windows-style INI
file support to your programs.
Online Help The entire function reference as a BP7 help file.
And, of course, you will be a bonafide owner of GOLD and will be
able to continue to use the product beyond the 30 day evaluation
period, and you will be able to distribute EXEs built using GOLD
without paying royalties.
5) LIMITED DISTRIBUTION LICENSE
-------------------------------
Permission is granted to any individual or business to distribute
this Shareware version of GOLD, provided they convey a complete and
unaltered copy of the entire package, and provided they claim no
ownership of these products.
TechnoJock Software, Inc. may revoke any permissions granted here,
by notifying you in writing.
▐▀▀▀▌ ▐ ▐ ▌ ▐
▐ ▌ ▐ ▐ ▌ ▐
▐ ▌▐▀▀▀▌ ▐ ▐ ▐▀▀▀▌ ▐▀▀▀ ▐▀▀▀▌▐▀▀▀ ▐ ▐ ▀▀█
▐ ▌▐ ▌ ▐ ▐ ▐ ▌ ▐▄▄ ▐ ▌▐▄▄ ▐ ▐ █
▐▄▄▄▌▐ ▌ ▐ ▐ ▐ ▌ ▐▄▄▄ ▐ ▌▐▄▄▄ ▐ ▐▄▄▄█
▐
▐
6) INSTALLING ONLINE HELP IN BP 7.0
-----------------------------------
We have included a superb feature for users of Borland Pascal 7.0
(or later), an online help facility detailing all the procedures and
functions for GOLD. If you installed GOLD and checked the online
help selection, the TTTGOLD.HLP file will have been transferred to
your system.
Take the following steps to integrate GOLD's on-line help with the
Borland IDE:
1. Move the compiled help file, TTTGOLD.TPH, to the same directory
where BP.EXE is located, this is typically \BP\BIN.
2. Execute Borland Pascal.
3. Select Help Files from the IDE's main menu -- the Help options
will be displayed. From the file selection dialog select
TTTGOLD.TPH and press OK.
The online help will now be integrated with BP's own help.
Note: Your specific configuration may affect your ability to load and
use TTTGOLD.TPH. The GOLD Online Help contains extensive information
on over 700 pascal routines designed to speed up your development time.
As you attempt to install TTTGOLD.TPH, you may receive a message
indicating that the help index is too large. To resolve this, return
to the HELP FILES menu choice and deselect some of the help files
that you may not need. Borland has included several help features
that you may not use on a regular basis.
Be sure to save these options so that the help file will load each
time you use the environment.
▐█ ▌ ▐ ▀▀█
▐ █ ▌ ▐ █
▐ █ ▌ ▐▀▀▀ ▐ ▌ ▌ ▐▄▄▄█ ▐▄▄ ▐▀▀▀▌▐▀▀▀ █▀▀▀
▐ █ ▌ ▐▄▄ ▐ ▌ ▌ ▐ ▐ ▐ ▌▐ █▄▄▄
▐ █▌ ▐▄▄▄ ▐▄▄▌▄▌ ▐ ▐ ▐▄▄▄▌▐▄▄▄ ▄▄▄█
7) NEW PROCEDURES AND FUNCTIONS
--------------------------------
Below are some additional procedures and functions that were added to
GOLD after the documentation went to press. Note that these routines
are included in the unabridged on-line help.
ScrollForceCase (GOLDIO2)
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Purpose: Controls automatic case adjustments in scrolling string
fields.
Syntax: ScrollForceCase(FieldID:byte; FCase: gCase);
Remarks: Field ID is the number of the scroll field whose case
adjustment will be set. FCase is a member of the enumerated
type gVase and may have one of the following values:
Upper, Lower, Proper and Leave.
See Also: ScrollField
Example:
ScrollForceCase(11,Proper);
*******
SetDefaultButton
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ (GOLDIO)
Purpose: Assigns a new default button to the current I/O form.
Syntax: SetDefaultButton(FieldID:byte);
Remarks: FieldID is the number of the button field that will be
assigned the default button status. Pass a FieldID value
of zero (the number 0) when you do not want a default
button. No validation checks are performed, so be sure
to pass the FieldID of a button field. This procedure is
designed for use in a hook when changing the identity of
the default button; use ButtonDefaultField to assign the
default button when defining a form.
See Also: ButtonDefaultField
Example:
SetDefaultButton(4);
*******
MemoReAssignSLL (GOLDMEMO)
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Purpose: Advises Gold that the contents of an SLL has been updated
and that the MemoCfg variable needs to reflect the changes.
Syntax: MemoReAssignSLL(var MemoDetails: MemoCfg;
var MemoSource: SingleLL);
Remarks: The first parameter is the memo configuration which will
be used to display the memo. The second parameter is the
SLL variable that was originally assigned with the
MemoAssignSLL function. Use this procedure when the
contents of the SLL have been updated on the fly (i.e. not
by editing the memo manually).
See Also: MemoAssignSLL
Example:
procedure DatabaseToScreen(RecNo:longint);
{}
begin
with EmpRec do
begin
EmpName := DbGetFldString(RecNo,1);
Dept := DbGetFldString(RecNo,2);
if DbGetMemoRecNum(RecNo,3) = 0 then {no memo}
begin
SLLSetActiveList(JobDesc);
SLLEmptyList;
end
else
DbGetFldMemo(RecNo,3,MemoFldVar);
MemoReAssignSLL(MemoFldVar,JobDesc);
end;
end; { DatabaseToScreen }
*********
▐▀▀▀▌ ▌ ▐▀▀▀▀▄ ▐
▐ ▌ ▐ █ ▐▀▀
▐ ▐▀▀▀▌▐ ▌ ▐ █ ▐ ▌ █▀▀▀ ▐
▐ ▀▌▐ ▌▐ ▐▀▀▀▌ ▐ █ ▐ ▌ █▄▄▄ ▐
▐▄▄▄▌▐▄▄▄▌▐▄▄▄ ▐▄▄▄▌ ▐▄▄▄▄▀ ▐▄▄▄▌ ▄▄▄█ ▐▄
8) GOLD DUST
------------
If there is a particular aspect of Gold which is not clearly understood
by the users, we will release a brief "white paper" explaining the
subject more clearly. These papers are known as "Gold Dust" and they
will be available online as well as in this file.
At present we only have one Gold Dust paper (below) which discusses the
notion of database handles.
┌────────────────────────────────────────────────────────────────────────┐
│ ARTICLE 0001 Assigning and using Handles with a database. │
└────────────────────────────────────────────────────────────────────────┘
The entire framework of database management in GOLD is based on the
"database handle". When opening a database using DbOpenDataSet, which
is the recommended process, it is important to assign this open
process to a handle. For example,
var Handle: integer;
begin
Handle := DbOpenDataSet(<DataFileName>);
if Handle <> 0 then
DoSomething;
DbCloseDataBase(Handle);
end.
This way it is possible to open multiple databases and change focus
from one database to another. That is, all the database functions
operate on the database with focus. To change focus, use
DbSetActiveDataBase and pass the handle of the database to which you
want to give focus.
A zero returned from opening a dataset indicates that the open was
not successful. Check the returned value of LastDBError to find out
why the failure occurred.
It is not recommended to open a dataset as follows:
if DbOpenDataSet(<DataFileName>) <> 0 then
DoSomethingElse;
This example does not make the proper assignment to a handle,
leaving no way to change focus or close the database.
If your application requires that you open more than one database
at a time, the variable name "Handle" would not be a good variable to
assign. Database1, Database2, etc. would be preferable names, or
perhaps the handle could be named after the specific database,
VeggieFile, MeatFile, BeverageFile. Use your own set of rules here.
Just remember, each database gets its own handle, whatever naming
convention you use.
You may close a specific data file by passing its handle to the close
process, DbCloseDatabase.
var Handle: integer;
begin
Handle := DbOpenDataSet(<DataFileName>);
if Handle <> 0 then
DoSomething;
DbCloseDataBase(Handle);
end.
DbCloseAllDatabases closes all currently open databases and so
requires no parameters be passed. This also disposes of all handles.
END OF ARTICLE 0001